Grokking SQL for Tech Interviews
Rate this course
Ask Author
Contribute
Back to course home

1% completed

Vote For New Content
Introduction
Course Overview
What is RDBMS?
What is SQL?
A Quick Review of SQL
Read data from table
WHERE Clause
Operators
Handle NULLs in SQL
DISTINCT Clause
ORDER BY Clause
LIMIT and OFFSET
GROUP BY
HAVING
Aggregate Functions
Order of Execution
Order of SQL Query Execution
SQL Functions
Number Functions
String Functions
Date Functions
Nested Queries
Nested Query
Types of Subqueries
JOINS
Introduction
INNER JOIN
LEFT OUTER JOIN
RIGHT OUTER JOIN
FULL OUTER JOIN
SELF JOIN
SET Operations
What are SET operations?
UNION
INTERSECT
EXCEPT
A Quick Review of DDL
Keys in SQL
CREATE
ALTER
DROP
TRUNCATE
Indexes
A Quick Review of DML
INSERT
UPDATE
DELETE
Database Backup & Restore
Backup Database
Restore Database
Interview Problems - Easy
1. Major Cities
2. Not boring movies
3. Triangle Judgement
4. Biggest Single Number
5. Product Sales Analysis I
6. Product Sales Analysis II
7. Game Play Analysis I
8. Game Play Analysis II
9. Queries Quality and Percentage
10. Average Selling Price
11. Weather Type in Each Country
12. Students and Examinations
13. Ads Performance
14. Group Sold Products By The Date
15. Employee Email Verification
16. Sellers With No Sales
17. Average Time of Process
18. Find Followers Count
19. Ad-Free Sessions
20. Bikes Last Time Used
21. Daily User Engagement Levels
22. Employee Attendance Record
23. Library Book Loans
24. Customer Purchase Summary
25. Long Comments (Easy)
26. Unused Accounts
27. Patient Appointment No-Shows
28. Books and Authors
29. High School Attendance
30. Employee Absences
31. Green Product Identification (Easy)
32. Employee Department Exclusion (Easy)
33. Sales Person (Easy)
34. Employee Task Tracking (Easy)
1. Winning Candidate
2. Second Degree Follower
3. 2nd Highest Salary
4. Game Play Analysis III
5. Game Play Analysis IV
6. Active Businesses
7. Product Price on a Specific Date
8. Monthly Transactions II
9. Team Scores in Football Tournament
10. Page Recommendations
11. Running Total for Different Genders
12. Evaluate Boolean Expression
13. Active Users
14. Find Interview Candidates
15. Suspicious Bank Accounts
16. Order Fulfillment Rate (Medium)
17. Last Person to Fit in the Elevator (Medium)
18. Retail Expansion Analysis (Medium)
19. Employee Collaboration Networks (Medium)
20. Second Fastest Time in Races (Medium)
1. Trips and Users
2. Human Traffic of Stadium
3. Students Report By Geography
4. Game Play Analysis V
5. Number of Transactions per Visit
6. Find the Quiet Students in All Exams
7. First and Last Call On the Same Day
8. Build the Equation
9. Longest Winning Streak
10. Dynamic Pivoting of a Table
11. Dynamic Unpivoting of a Table
12. Generate the Invoice
13. Popularity Percentage
14. Viewers Turned Streamers
15. Status of Flight Tickets
1. High Performing Employees (Easy)
2. Student Course Averages (Easy)
3. Library Book Checkout Percentage (Easy)
4. Employee Performance and Improvement Rate (Easy)
5. Find Popular Posts (Easy)
6. Main Office Assignment for Each Employee (Easy)
7. Rectangle Validation (Easy)
8. Library Book Checkouts by Date (Easy)
9. Same-Day Appointment Fulfillment (Medium)
10. Departments with High Earning Employees (Medium)
11. Students Who Attended All Courses (Medium)
12. Library Book Checkouts First Year (Medium)
13. Repeated Values in Sequence (Medium)
14. School Top Achievers by Subject (Hard)
21. Daily User Engagement Levels

Problem Statement

Table: Users
Each row of this table contains the ID and the name of one user.

+---------------+---------+
| Column Name   | Type    |
+---------------+---------+
| user_id       | int     |
| user_name     | varchar |
+---------------+---------+
user_id is the primary key for this table.

Table: Engagement
Each row of this table records the daily engagement score of a user.

+---------------+------+
| Column Name   | Type |
+---------------+------+
| user_id       | int  |
| engagement    | int  |
| date          | date |
+---------------+------+
(user_id, date) is the primary key for this table.

Write a solution to find the engagement level of each user for February 2020.

The engagement levels are defined as:

  • Low if the average engagement is less than 20,
  • Medium if the average engagement is between 20 and 60 (inclusive), and
  • High if the average engagement is greater than 60.

Return the result table in any order.

Example

Input:

Users table: +---------+-----------+ | user_id | user_name | +---------+-----------+ | 1 | Alice | | 2 | Bob | | 3 | Charlie | | 4 | David | | 5 | Eve | +---------+-----------+
Engagement table: +---------+------------+------------+ | user_id | engagement | date | +---------+------------+------------+ | 1 | 10 | 2020-02-01 | | 1 | 25 | 2020-02-02 | | 2 | 30 | 2020-02-01 | | 2 | 40 | 2020-02-03 | | 3 | 65 | 2020-02-05 | | 3 | 70 | 2020-02-06 | | 4 | 23 | 2020-02-07 | | 4 | 24 | 2020-02-08 | | 5 | 55 | 2020-02-09 | | 5 | 60 | 2020-02-10 | +---------+------------+------------+

Output:

+-----------+----------------+ | user_name | engagement_level | +-----------+----------------+ | Alice | Low | | Bob | Medium | | Charlie | High | | David | Medium | | Eve | Medium | +-----------+----------------+

Try It Yourself

MYSQL

. . . .

Users =

Engagement =

Solution

To determine the engagement level of each user for February 2020, we need to calculate the average engagement score for each user during that month and categorize them based on the defined thresholds. The process involves joining the Users and Engagement tables, filtering the relevant dates, computing the average engagement, and assigning the appropriate engagement level.

  • Join Users and Engagement Tables: Combine user information with their corresponding engagement records.
  • Filter Engagement Records for February 2020: Select only the engagement data that falls within February 2020.
  • Calculate Average Engagement: Compute the average engagement score for each user during the specified period.
  • Assign Engagement Levels: Categorize users as Low, Medium, or High based on their average engagement scores.

SQL Query

SELECT user_name, CASE WHEN AVG(engagement) < 20 THEN 'Low' WHEN AVG(engagement) <= 60 THEN 'Medium' ELSE 'High' END AS engagement_level FROM Users JOIN Engagement ON Users.user_id = Engagement.user_id AND YEAR(date) = '2020' AND MONTH(date) = '02' GROUP BY user_name;

Step-by-Step Approach

Step 1: Join Users and Engagement Tables for February 2020

Combine user information with their engagement records that occurred in February 2020.

SQL Query:

SELECT Users.user_name, Engagement.engagement FROM Users JOIN Engagement ON Users.user_id = Engagement.user_id AND YEAR(Engagement.date) = '2020' AND MONTH(Engagement.date) = '02';

Explanation:

  • SELECT Users.user_name, Engagement.engagement:
    • Retrieves the user's name and their engagement score.
  • FROM Users JOIN Engagement ON ...:
    • Performs an inner join between Users and Engagement tables based on user_id.
  • AND YEAR(Engagement.date) = '2020' AND MONTH(Engagement.date) = '02':
    • Filters the engagement records to include only those from February 2020.

Output After Step 1:

+-----------+------------+ | user_name | engagement | +-----------+------------+ | Alice | 10 | | Alice | 25 | | Bob | 30 | | Bob | 40 | | Charlie | 65 | | Charlie | 70 | | David | 23 | | David | 24 | | Eve | 55 | | Eve | 60 | +-----------+------------+

Step 2: Calculate Average Engagement for Each User

Compute the average engagement score for each user during February 2020.

SQL Query:

SELECT user_name, AVG(engagement) AS avg_engagement FROM Users JOIN Engagement ON Users.user_id = Engagement.user_id AND YEAR(Engagement.date) = '2020' AND MONTH(Engagement.date) = '02' GROUP BY user_name;

Explanation:

  • SELECT user_name, AVG(engagement) AS avg_engagement:
    • Selects each user's name and calculates their average engagement score.
  • GROUP BY user_name:
    • Groups the data by user_name to perform the aggregation for each individual.

Output After Step 2:

+-----------+----------------+ | user_name | avg_engagement | +-----------+----------------+ | Alice | 17.50 | | Bob | 35.00 | | Charlie | 67.50 | | David | 23.50 | | Eve | 57.50 | +-----------+----------------+

Step 3: Assign Engagement Levels Based on Average Scores

Categorize each user as Low, Medium, or High based on their average engagement scores.

SQL Query:

SELECT user_name, CASE WHEN AVG(engagement) < 20 THEN 'Low' WHEN AVG(engagement) <= 60 THEN 'Medium' ELSE 'High' END AS engagement_level FROM Users JOIN Engagement ON Users.user_id = Engagement.user_id AND YEAR(Engagement.date) = '2020' AND MONTH(Engagement.date) = '02' GROUP BY user_name;

Explanation:

  • CASE WHEN ... THEN ...:
    • Assigns engagement levels based on the calculated average engagement:
      • < 20: Low
      • <= 60: Medium
      • > 60: High

Final Output:

+-----------+-------------------+ | user_name | engagement_level | +-----------+-------------------+ | Alice | Low | | Bob | Medium | | Charlie | High | | David | Medium | | Eve | Medium | +-----------+-------------------+
20. Bikes Last Time Used
22. Employee Attendance Record
Mark as Completed

On this page

Problem Statement

Example

Try It Yourself

Solution

SQL Query

Step-by-Step Approach